Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1133

reference: 859-tree-1
name: 1133
tree-preservation-order: undefined
859-tpo-1
uprn
address-text
point: POINT (-0.954633 50.868060)
geometry: MULTIPOLYGON (((-0.954604 50.868057,-0.954609 50.868068,-0.954616 50.868072,-0.954632 50.868075,-0.954649 50.868072,-0.954660 50.868063,-0.954661 50.868058,-0.954660 50.868052,-0.954656 50.868047,-0.954642 50.868040,-0.954633 50.868039,-0.954624 50.868040,-0.954616 50.868043,-0.954606 50.868051,-0.954604 50.868057)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL